Data Services Developer's Guide : Creating Data Source Metadata
This page last changed on Jan 09, 2008 by tkatz.
eDocs Home > BEA AquaLogic Data Services Platform 3.0 Documentation > Data Services Developer's Guide
|
Source Type |
Venue |
---|---|
Relational (including tables, views, stored procedures, and SQL) | JDBC |
Web services (WSDL files) | URI, UDDI, WSDL |
Delimited (CSV files) | File-based data, such as spreadsheets. |
Java functions (.java) | Programmatic |
XML (XML files) | File- or data stream-based XML |
When information about physical data is developed during the creation of physical data services, two things happen:
The introspection process is done through the Physical Data Service Creation wizard. This wizard introspects available data sources and identifies data objects that can be rendered as operations for either entity or library data services. Once created, physical data services become the building-blocks for queries and logical data services through a series of pragmas created in the query source.
For example, the following source resulted from importing a Web service operation:
(::pragma function <f:function xmlns:f="urn:annotations.ld.bea.com" kind="read" nativeName="getCustomerOrderByOrderID" nativeLevel1Container="ElecDBTest" nativeLevel2Container="ElecDBTestSoap" style="document"/>: declare function f1:getCustomerOrderByOrderID($x1 as element(t1:getCustomerOrderByOrderID)) as schema-element(t1:getCustomerOrderByOrderIDResponse) external;
Notice that the imported Web service is described as a "read" function in the pragma. "External" refers to the fact that the schema is in a separate file.
For some data sources such as web services imported metadata represents functions which typically return void (in other words, these functions do something other than return data). Such routines are sometimes called side-effecting functions or procedures.
The following source resulted from importing Web service metadata that includes an operation that has been identified as a side-effecting procedure:
(::pragma function <f:function xmlns:f="urn:annotations.ld.bea.com" kind="hasSideEffects" nativeName="setCustomerOrder" style="document"/>: declare function f1:setCustomerOrder($x1 as element(t3:setCustomerOrder)) as schema-element(t3:setCustomerOrderResponse) external;
In the above pragma the function is identified as "hasSideEffects".
![]() |
Document generated by Confluence on Jan 15, 2008 11:02 |